I keep getting a particular type of crash report for my macOS app (FAF) that I cannot figure out. Here's the top of the stack trace which all reports have in common: Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libobjc.A.dylib … objc_msgSend + 29 1 com.apple.AppKit … -[NSPathControl _performDragOfCell:fromMouseDown:] + 130 2 com.apple.AppKit … -[NSPathControl mouseDown:] + 300 3 com.apple.AppKit … -[NSWindow(NSEventRouting) _handleMouseDownEvent:isDelayedEvent:] + 4961 What I figured out so far: Is triggered by a click or double click on a segment of the NSPathControl. For some users it has been happening more than once, but not often enough for me to figure out what's behind it. I have not been able reproduce it even once. Leads to a "Segmentation fault: 11" Happens in macOS versions from at least 10.8 until the most current (11.4). In both Intel and ARM code. The call stack does not show any of my own code involved. The app's other threads are all idle. Some reports do not list any non-Apple extensions or dylibs as far as I can tell. When I googled "crash NSPathControl setHighlighted", I could only find a single other mention of it, but that crash even happened in Finder, on OSX 10.8.1. The person reporting it had quite a few other system extensions loaded but eventually figured out that it got fixed when he changed his Wacom tablet's behavior from not issuing a triple click any more. I tried to create triple clicks, along with combined drags, even using SteerMouse to have a triple click event generated by a separate mouse button, but to no avail. Has anyone else seen this type of crash? Any idea what may be behind this? I have two complete crash reports (with only some privacy related lines removed at the top) uploaded here: https://gist.github.com/tempelmann/5c519244ffc7a485afa66d546a9b9712 https://gist.github.com/tempelmann/315f8122b8079637cb5a9bf299ac380a

I'm making (non-sandboxed) Mac applications for in-house use (which is a controlled, and hence trusted, environment). I waste a lot of time debugging and meeting notarization and the many other app deployment requirements (entitlements, permissions for scripting other apps, accessing "protected" folders etc.). This is costly for us, too, both in time and financially. All these security measures should not be necessary in our controlled environment - we inherently trust our own software, after all. Is there some way to disable these checks, or at least some of them? Perhaps with special certificates that broadly grant all these permissions to all our own apps on our own Macs?

I have both a Mac Mini 2018 and a VMware (preview build 16530630) system with BS Beta 2 (20A4300b) running. Both offer the beta 3 update, even both the universal installer with 12.9 GB (which I used successfully to update the DTK, where I didn't get the automatic update offered yet), and the Intel-only installer with about 5-6 GB. I tried to use both installers on both machines, and every time there seems to be a kind of crash in the middle of installation, and then the system reboots into beta 2. Both systems are installated in their own APFS container (no sharing with 10.15.x). This should be the most basic config. The Mac Mini has about 35 GB of free space, and the BM even over 60 GB. That should be plenty. Any ideas how to fix that? Anyone else having the same problem? Or an idea how to find the log & error msgs the updater may report? I could, of course, re-install from scratch, but I'd only use that as a last resort. Still hoping this can be solved.

I am using this forum for the first time, and I'm not clear on the policies (to me this seems to be designed more like an Apple Store than a developer forum). The "Learn more about the forums" is of no help in this regard, and I have therefore no idea what the Post Visibility is for (i.e. maybe for beta software??). I mean, there isn't even a BigSur tag, yet?!? So I'll just post a few things here and see if I'm getting kicked out or silenced and then I know not to try this again. I mainly like to get some feedback in the form of "yes, I can confirm this issue" so that I have a better idea what is a bug and what is just me doing something wrong or doesn't affect anyone else. Issues with BS Beta 3 on a DTK system: I tried running Geekbench 4 and 5. Both run, but when they try to report the results, both open Safari, which then tell me that the URL is somehow invalid. So I never succeed in seeing the results. Does this work for others? 2. I have attached a USB 3.1 SSD via a USB-C-to-C cable to the Mac. When I read large amounts of data (e.g. a 10 GB file) from it, then often the file read comes to a stall, and it takes very long to finish. When I use a USB-C-to-A cable (A-connector goes into the Mac), so that it's USB 3.0, then there's no such stalling. Can anyone else reproduce this? 3. Whenever I try to trash (i.e. delete, as it doesn't have a Trash folder) an app bundle from my NAS that's connected via SMB, I get a system (kernel?) crash with a hard reboot. Anyone else?